feat: implement Browse AI plugin against official v2 API - #1042

Someone is attempting to deploy a commit to the corsair Team on Vercel.

A member of the Team first needs to authorize it.

No actionable comments were generated in the recent review. 🎉

sequenceDiagram
  participant CorsairPlugin
  participant EndpointOperation
  participant browseaiCall
  participant makeBrowseaiRequest
  participant BrowseAIAPI
  CorsairPlugin->>EndpointOperation: Invoke typed operation
  EndpointOperation->>browseaiCall: Validate input and pass schema
  browseaiCall->>makeBrowseaiRequest: Pass API key and request options
  makeBrowseaiRequest->>BrowseAIAPI: Send v2 HTTP request
  BrowseAIAPI-->>makeBrowseaiRequest: Return JSON response or HTTP error
  makeBrowseaiRequest-->>browseaiCall: Return parsed result or error
  browseaiCall-->>EndpointOperation: Return typed result
  EndpointOperation-->>CorsairPlugin: Log completed audit event

• Fix all pre-merge checks with AI

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands.}

Greptile Summary

The PR adds a Browse AI provider plugin backed by the official v2 API.

• Implements API-key authentication and typed operations for status, robots, tasks, monitors, and webhooks.
• Validates endpoint inputs and API responses with Zod schemas.
• Prevents automatic replay of non-idempotent write requests while retaining rate-limit handling for safe operations.
• Adds package configuration and endpoint, transport, schema, authentication, and error-handling tests.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains; the previously reported output-validation bypass and non-idempotent write replay have both been addressed.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant App as Corsair application
    participant Plugin as Browse AI plugin
    participant Client as Browse AI client
    participant API as Browse AI v2 API
    App->>Plugin: Invoke typed endpoint
    Plugin->>Plugin: Parse input schema
    Plugin->>Client: Request with endpoint output schema
    Client->>API: Bearer-authenticated HTTP request
    API-->>Client: JSON response
    Client->>Client: Parse output schema
    Client-->>Plugin: Validated result
    Plugin-->>App: Typed response

_{Reviews (2): Last reviewed commit: "chore: merge main into feat/browserai-pl..." | Re-trigger Greptile}

Plugin PR scorecard — packages/browseai

Rules: PLUGIN_PR_RULES.md · re-runs on every push

Hey @TanayGurav19, thanks for the contribution! 🏴‍☠️ Before a maintainer reviews, please fix the items below — the review re-runs automatically on your next push.

Must fix

• P1 packages/browseai/client.ts:62 — Output validation is bypassed
  When Browse AI returns data that differs from the declared output schema, makeBrowseaiRequest returns the unchecked generic response and the runtime does not parse the registered schema, causing callers to receive malformed data as the declared TypeScript type.

Rule Used: Every endpoint must validate inputs and outputs wi... (source)

Knowledge Base Used: Provider plugin implementation conventions

• P1 packages/browseai/error-handlers.ts:30 — Retries replay write operations
  When a write continues receiving HTTP 429 after the client exhausts its three retries, this handler retries the entire endpoint up to five more times, causing one logical request to send roughly two dozen non-idempotent writes and potentially create duplicate tasks, monitors, bulk runs, or webhooks.

Knowledge Base Used: Provider plugin implementation conventions

If anything remains after your next push, a maintainer will take it from there and do the final review and merge.

@greptile

Maintainer review needed

Automated rounds are exhausted. Remaining findings:

• P1 packages/browseai/client.ts — Output validation is bypassed
  When Browse AI returns data that differs from the declared output schema, makeBrowseaiRequest returns the unchecked generic response and the runtime does not parse the registered schema, causing callers to receive malformed data as the declared TypeScript type.

Rule Used: Every endpoint must validate inputs and outputs wi... (source)

Knowledge Base Used: Provider plugin implementation conventions

• P1 packages/browseai/error-handlers.ts:33 — Retries replay write operations
  When a write continues receiving HTTP 429 after the client exhausts its three retries, this handler retries the entire endpoint up to five more times, causing one logical request to send roughly two dozen non-idempotent writes and potentially create duplicate tasks, monitors, bulk runs, or webhooks.

Knowledge Base Used: Provider plugin implementation conventions